Please note that this may degrade single-threaded IO performance on Windows (and I don't think it does anything on Unix?). For some reason, going through Overlapped IO performs much worse.

Further discussion: https://github.com/Cysharp/Utf8StreamReader?tab=readme-ov-file#optimizing-filestream

I believe there's no reason to keep FileStream non-async by default

Making this async will cause all synchronous usage to be sync-over-async on Windows. We should not do that.

Thanks for the thought, though.

Can we instead add overloads which have a FileOptions parameter to those APIs?
It's really convenient to use File.OpenWrite instead of instantiating a FileStream manually.

Can we instead add overloads which have a FileOptions parameter to those APIs? It's really convenient to use File.OpenWrite instead of instantiating a FileStream manually.

#24698

Can we instead add overloads which have a FileOptions parameter to those APIs? It's really convenient to use File.OpenWrite instead of instantiating a FileStream manually.

#24698

That one didn't cover File.OpenWrite and File.OpenRead.